Magnum One/Magnum One (Mid-American Digital) (Disc Manufacturing).iso/d3/clarion.arc/PTUTOR.HLP

Clarion Help | 1991-07-24 | 61KB | 1,110 lines

 This is the Base Window.
 Notice that
 applications
 found in this
 directory are
 listed here.
 The bottom line lists seven options.
 /Run Selected Application
Application: PHONES
Files
     Procedures
MEMORY
MAIN_MENU (Menu) - Directory Menu
PHONES
SHO_NAME (Table) - Directory by Name
STATES
UPD_PHONES (Form) - Update Directory
SHOW_STATE (Table) - State Listing
UPD_STATE (Form) - State Listing
SHO_COMPANY (Table) - Directory by Company
UPD_PHONES (Form) - Update Directory
SHOW_STATE (Table) - State Listing
UPD_STATE (Form) - State Listing
RPT_NAME (Report) - Directory by Name
RPT_COMPANY (Report) - Directory List by Company
CARDS (Report) - Rolodex Cards
LABELS (Report) - Mailing Labels
RETURN
Ins to Add
Enter to Change
Del to Delete
Tables
Main Menu
Bright White On Blue
MM/DD/YY
Show File by Key
  Print File by Ke
  Show File by Key
LOCATE:
Update File
  Prompt:
  Prompt:<<,<<#.##
  Prompt:MM/DD/YY
Press B to toggle Blink
  Add
Enter
/ /!/"/#/$/%/&/'/(/)/*/+/,/-/.
?0?1?2?3?4?5?6?7?8?9?:?;?<?=?>
O@OAOBOCODOEOFOGOHOIOJOKOLOMON
_P_Q_R_S_T_U_V_W_X_Y_Z_[_\_]_^
o`oaobocodoeofogohoiojokolomon
 The black bar
 indicates the current application.  This applies to
 the [Run] and [Modify] options.  The bar can be moved with the Up
 and Down
 keys to select the desired application.
The CLARION Personal Developer
Introduction
Files and Keys
Procedures
Using Quick Start
A Preview of the Professional Developer
     Please Choose a tutorial topic
 QRun
Modify
Create
Options
Import/Export
Tutorial
 This tutorial is presented in a page-by-page format.
 You may turn pages manually, or you may have them
 turned automatically for you.
 To continue, please press
[M] for manual,
[A] for automatic, or
[Esc] to return to DOS.
 Bill Smith
 123 W. East St.
 Coral Way, FL
 (305)
-1234
 Birthday: 5/23
 Mary Jones
 765 N. West Rd.
 Coral Way, FL
 [phone]
 Birthday: 7/24
 Peter Andrews
 1021 E. 100th Way
 Coral Way, FL
 [phone]
 Birthday: 2/14
 Nancy Mathews
 1315 S. 200th Ave.
 Coral Way, FL
 [phone]
 Birthday: 9/30
 Bill Smith
 Nancy Mathews
 Mary Jones
 Peter Andrews
 1021 E. 100th Ave.
 Coral Way, FL
 [phone]
 Birthday: 2/14
Tables
Main Menu
Bright White On Blue
MM/DD/YY
Show File by Key
Track
  Print File by Ke
Fields
  Show File by Key
Selected Field
Tables
LOCATE:
Track
Fields
Prompts
Forms
Update File
Track
Prompts
  Prompt:
Fields
  Prompt:<<,<<#.##
Selected Field
  Prompt:MM/DD/YY
Message Field
  Add
Enter
 If you have seen and understood the previous tutorials,
 you now know enough to accomplish something useful with
 Personal Developer.
 After you have reviewed Chapter Two in your user's manual,
 and you have mastered the Quick Start method, move on to
 Chapter Three.  In Chapter Three you will learn the
 Custom Method of application design.
 You will soon be familiar with the manner in which
 Personal Developer applications are constructed.  Then
 The [Create] option allows you to make a
 new application (one that does not appear
 in the list of applications found in this
 directory.)
 5Design New Application
 0Create
Field
  Field Name :ADDRESS
  Description:Contact Address
  Type
:Character
  Length
  Picture
:@s30
  Choices
  Type Mode  :AsIs
Ins  Ovr  AsIs
  Required
Yes  No
  Immediate  :No
Yes  No
  Num Lock
Yes  No
  Left Just  :No
Yes  No
  Upper Case :No
Yes  No
Record
Address
     City
St  Zip
Phone
B-DayNumber
Bill Smith
123 W. East St.
Coral Way
(305)
-1234
Mary Jones
765 N. West Rd.
Coral Way
[phone]
Peter Andrews
1021 E. 100th Way
Coral Way
[phone]
Nancy Mathews
1315 S. 200th Ave.
Coral Way
[phone]
(PHONEBK.DAT)
(ZIPCODE.DAT)
Address
Phone
B-Day
St  No
Bill Smith
123 W.East St.
(305)
-1234
33064
Pompano Bch
Mary Jones
765 N.West Rd.
[phone]
Coral Way
Peter Andrews
1021 E.100 Way
[phone]
Nancy Mathews
1315 S.200 Ave
[phone]
File: PHONES
Prefix: PHN
Fields
 ,Keys
NAME (Character 30) - Name of Contact
BY_NAME (Key)
COMPANY (Character 30) - Company name
ADDRESS (Character 30) - Contact Address
CITY (Character 28) - Contact City
BY_COMPANY (Key)
STATE (Character 2) - Contact State
COMPANY
ZIP (Character 6) - Contact Zip Code
PHONE (Numeric 10.0) - Contact Phone
Ins to Add
Enter to Change
Del to Delete
 Personal Developer is a software package that lets you
 conceive and create your very own programs (even if you
 are not a programmer) to organize, maintain, and produce
 reports on your data.
 By "data" we simply mean any kind of related information
 that is important to you.  A common example is a list of
 names of people that you know along with their addresses,
 phone numbers, and even perhaps their birthdays and
 anniversaries.
 One way this sort of data can be organized is by noting
 each person's information on a separate 3x5 card.
 Many data base applications are more complicated than our
 example and require more than one data file.  Often the
 information in one file is "related" to the information
 in one or more other files.  We can say that there is a
 "relationship" between the files.  When we design a
 program to utilize those relationships we have what is
 called a "relational data base" application.
 In our example, we could notice that if
 our file becomes large, we could save
 disk space by making a separate file to
 be used as a zip code table.  We could
 only store the zip code in our PHONEBK
 file and use it to "look-up" the city
 and state when we need them.
 Now the PHONEBK.DAT data file contains the Zipcode field
 with the City and State fields part of a separate data
 file, ZIPCODE.DAT.  The Zipcode field is used as a related
 field to look-up City and State.
 The ZIPCODE file has a key file
 (ZIPCODE.K01) which uses the
 Zipcode field as a key component.
 You can look-up a City and State
 by using the Zipcode from
 PHONEBK.DAT to locate a record
 in ZIPCODE.DAT.
 Many of the sample applications that come with Personal
 Developer show examples of relating one or more files:
[ORDER] - an inventory part number in an order file is
used to look-up an item description and price.
[TEACHER] - a student I.D. is used to look-up a
student's full name.
[TRACKING] - a company's name is used to retrieve its
sales history from a sales tracking file.
And there are many more examples.
 Remember the Application Summary Window you saw
 briefly in the introductory tutorial?
 This is where you will begin the process of
 designing data files and keys for your programs.
 To modify an existing file definition, you move
 the selector bar to the desired file name and
 press Enter.
 Here you see the fields that make up the
 records of this file.  Fields can be added to
 a file, deleted from a file, or you can change
 information about a field.  The bar is used to
 select a field.  If you press enter, the Field
 window will appear.
 The Field window is where
 you define the character-
 istics of the fields in your
 file.  In later tutorials
 you will learn about field
 characteristics and how they
 affect screens and reports
 that you design.
 This side of the File window
 shows the keys
 that are used by your file.  New keys can be
 defined, or existing keys can be changed or
 deleted.  The selector bar is used to point
 to the desired key.  If you press Enter, the
 Key window will appear.
 The Key window is where you name your key and
 define its special characteristics.  Again,
 we will leave it to later tutorials to cover
 the meaning of each of the special key
 characteristics.
 We now have our important data
 recorded, but as a pile of
 cards it is not very useful to
 We need to organize our data
 into an ordered set called a
 "file".
 This concludes the tutorial on files and keys.  The goal
 of this tutorial was to present to you a number of terms
 and concepts that will be used in later tutorials and in
 your user's manual.
 Very little has been said yet about how to actually use
 Personal Developer, but please be patient.  We will get
 there very soon.  Before we do, however, please view one
 more conceptual tutorial.
 The next tutorial explains the concept of procedures.  You
 will build the programs that will use the files you design
 from building blocks called procedures.
 We now have a "file".
 It consists of a set of "records".
 Each record is a set of related pieces
 of information called "fields".  For
 example, the person's name is a field.
 And the street address is a field, and
 so is the city, etc.
 Remember we said that our
 file was an "ordered" set.
 Without order, a data file
 isn't of much use.  We
 chose to order this file
 in alphabetic order by the
 "Name" field.
 Ordering a file makes it
 possible for us to quickly
 find a specific record.
 In this case, we look up a
 record by name.
 In our example, we gave order to our
 file via a process called sorting.
 Sorting can be time consuming, but in
 this example it serves our purpose.
 However, what if we want to be able
 to keep our data ordered by more than
 one sequence.  Let's say we also want
 to be able to quickly locate a record
 by only knowing the phone number.
 Now our 3x5 card system begins to
 break down, and this is where your
 computer and Personal Developer can
 come to the rescue.
 With Personal Developer, you design data files to contain your information.
 In this case, a single data file replaces our 3x5 cards.  With a data file
 built by Personal Developer, you need not worry about the order in which the
 records are actually stored -- there is a better way.
 r(PHONEBK.DAT)
 With Personal Developer, after you
 design your data file you then design
 a "key" for your file.
 Your programs will use keys to
 identify and order the records in
 your data file.
 Every data file you design will have
 at least one key.  When you design a
 key, you will specify which field (or
 fields) you want to use to order your
 records.  The program that you create
 will build the key for you and auto-
 matically keep the key entries in the
 correct order -- every time you add,
 change, or delete a record in your
 data file.
 Personal Developer allows
 every file you design to
 have as many keys as it
 needs.  In our example, we
 wanted to be able to find
 records by phone number.
 Now the solution is easy.
 Simply design a second key
 for your data file.  This
 time, specify the "Phone"
 field as the "key component"
 for identifying and ordering
 records.
 We have now described what would become a data
 file (PHONEBK.DAT) and two key files (PHONEBK.K01
 and PHONEBK.K02) on your disk drive.  Three disk
 files in all, but together, when you build a
 program around them that lets you locate, add,
 change, and remove records and print reports, you
 have what can be called a "data base".
 The Import/Export function allows you to
 convert dBaseII, dBase
, DIF, and Comma-
 Delimited ASCII files into Clarion file
 format, and vice-versa.
 =Import and Export Files
 LImport/Export
 How to run this Tutorial
 You can change the viewing mode at any time by pressing
 for Manual
 for Automatic
 In either viewing mode
     the right arrow key
  turns to the next page, and
     the left arrow key
  turns to the previous page.
 How to run this Tutorial (continued)
 In manual viewing mode, the tutorial waits for you to press one of the
page turning keys.
 In automatic viewing mode, the tutorial gives you time to read a page,
then turns to the next page automatically.
You can speed up the tutorial by
pressing the gray + key
slow down the tutorial by
pressing the gray - key.
You can exit a tutorial by
pressing the Esc key.
 The next screen you see will be the Tutorial Main Menu.
 The Tutorial Main Menu will offer you a choice of
 tutorial topics.  Use the Up and Down arrow keys to
 select the tutorial you wish to see.  Then press Enter to
 begin the selected tutorial.
 We recommend that you view each tutorial, starting at the
 top of the list with "Introduction."  Then move down the
 list, viewing each tutorial in its turn.  You may wish to
 view some of the tutorials more than once.
 The tutorials will not take the place of your user's
 manual, but we hope they help you get "up and going" with
 Personal Developer quickly.
 Welcome to the Clarion Personal Developer -- your tool
 for creating your own custom database applications.
 You will find that creating applications with the
 Personal Developer is fast and fun -- and you need no
 prior programming knowledge.
The power of the Personal
 Developer allows you to create a wide range of programs,
 each with your own "look and feel."
 To load the Clarion Personal Developer
First, change the current directory to be the
     PCLARION directory.
Then, type PCLARION and press Enter.
 For example,
 pressing Enter with
 the bar on PHONES
 tells Personal
 Developer to run
 the Personal
 Telephone Directory
 sample application.
 If you were to press Enter with
 the selector bar on PHONES, the
 Application window appears as
 you see here.
 Here you name your application,
 describe what it does, and name
 the procedure where you want
 the program to start.
 After entering the Application
 window, the Application Summary
 window appears as you see here.
 This window displays a schematic
 of the files and procedures that
 make up the Personal Telephone
 Directory sample application.
 Don't worry about what all this
 means for now.  You will learn
 more about files and procedures
 in their tutorials.
  (PHONEBK.K01)
Peter Andrews
Mary Jones
Nancy Mathews
Bill Smith
  (PHONEBK.K02)
[phone]
[phone]
[phone]
(305)
-1234
(ZIPCODE.K01)
33064
  Key Name
:BY_NAME
  Unique Key
Yes  No
Auto-number :No
Yes  No
  Case Sensitive:No
Yes  No
  Exclude Nulls :No
Yes  No
IINTRO
FFILES
PPROCS
UQUICK
APROF
 Introduction
Files and Keys
Procedures
 !Using Quick Start
A Preview of Professional Developer
 The [Modify] option allows you
 to make changes and enhancements
 to the indicated application.
 6Modify Selected Application
 "Modify
Application
  Application
:PHONES.APP
  Description
:Personal Telephone Directory
  Base Procedure:MAIN_MENU
Modify Selected Application
 ,Modify
 If Enter is pressed on [Options], the
 Options window will appear.  There
 are seven options you can set.
 8Change Default Options
 =Options
Options
  Directory Name
:C:\PCLARION\
  Create Listings
Yes  No
  Set Keyboard Locks
Yes  No
  Enhanced Keyboard
Yes  No
  Set Quick Start Colors:No
Yes  No
  Display Description
Yes  No
  Display Sign-on Screen:Yes
Yes  No
 KChange Default Options
 GOptions
 [Directory Name] shows the directory in which
 you are working.  You may enter a different
 directory on this line.  Simply type in the
 name of the directory and press Enter.
 Personal Developer will validate the name you
 enter.
C:\PCLARION\
 When first starting the Personal Developer, an initial help
 screen appears providing helpful information for novice
 users.  If you do not wish to see this screen each time you
 log on, select [No] for [Display Sign-on Screen].
 This concludes the introductory tutorial.  This tutorial
 was intended to introduce you to the Personal Developer
 Base window and its five options.  You should now proceed
 to the tutorial on Files and Keys where some important
 concepts will be covered.
 When you create or modify a program, Personal Developer writes your program
 in the Clarion programming language.  Clarion is a powerful, modern, high-
 level computer language -- designed to easily produce the sort of programs
 you will be creating.  If you specify [Yes] to [Create Listings], we make it
 possible for you to see the actual language statements of your program.  The
 next time your program is generated, a "listing" file will be created on
 your disk drive.  The file will be named "<application name>.LST" and it may
 be printed on your printer or viewed with the DOS TYPE command.
 Personal Developer will, at times, automatically set
 the state of the Scroll Lock, Num Lock, and Caps Lock
 keys.  This is intended to be for your convenience,
 but you may disable this feature, if you wish, by
 specifying [No] to [Set Keyboard Locks].  (Or, if
 your keyboard fails to respond while you are running
 an application, try setting this line to [No].)
 If your computer supports and uses an enhanced keyboard,
 select [Yes] at [Enhanced Keyboard].  This will enable
 you to use the F11 and F12 keys in your application.
 If your computer does not support or use an enhanced
 keyboard, select [No].  (Or, if your keyboard fails to
 respond while running an application, try setting this
 line to [No].)
 Personal Developer allows you to set the default colors or
 your quick start windows.  If you wish to change any of
 your colors, move the selector to [Yes] and press Enter.
 These are the quick start
 windows that can be changed.
 As you change colors, you can
 see how the colors will look
 in the small windows here.
 You simply move the selector
 bar to the category of colors
 you wish to change and then
 press Enter.
 The active color is shown here
 and appears in a box on the
 control screen.  The cursor
 control keys are used to move
 the box to the color you desire.
 Pressing Enter will set a new
 active color on your quick start
 windows for the specified
 category.
 The description for each application is shown on the
 Base window to the left of each app.  To speed up the
 display of the Base window, this display of the des-
 criptions can be turned off.  Select [No] for [Display
 Descriptions] if you don't want the descriptions shown.
The CLARION Personal Developer
ASSETS
- Home Inventory
- Club Membership Roster
LIBRARY  - Books, Video Tapes, and Music
MEMOS
- Interoffice Memo Writer
ORDER
- Order Entry System
PHONES
- Personal Telephone Directory
TEACHER  - Grading and Class Organization
TRACKING - Sales Tracking
Modify
Create
Options
Import/Export
Tutorial
Personal Telephone Directory
Directory by Name
Directory by Company
Directory List by Name
     Directory List by Company
Rolodex Cards
Mailing Labels
 to point to the desired
Function and ENTER to select
 Instruction 1
 Instruction 2
 Instruction 3
 Instruction 4
(Procedure)
 Instruction ?
 Return
 (Procedure "A")
Instruction 1
(Procedure "B")
Instruction 2
 Instruction 1
 Instruction 2
(Call) "B"
. . .
Instruction 4
 Instruction ?
. . .
 Return
Instruction ?
Return
 (Procedure "A")
Instruction 1
(Procedure "B")
(Procedure "C")
Instruction 2
 Instruction 1
 Instruction 1
 Instruction 2
 Instruction 2
(Call) "B"
 Instruction 3
 (Call) "C"
Instruction 4
 Instruction 4
. . .
 Instruction 4
 Return
Instruction ?
 Return
Return
(Procedure "A")
 ?Inst. 1
(Procedure "B")
(Procedure "C")
Inst. 2
 Instruction 1
 Instruction 1
 Instruction 2
 (Call) "C"
Error !
 "B"
 Instruction 3
 (Call) "C"
Inst. 4
 (Call) "A"
Error !
 Instruction 4
 Return
Inst. ?
 Return
 'Return
 Programs that you create with Personal Developer are made
 up of two important components: files and procedures.
 Files were explained in the previous tutorial.
 This tutorial will cover procedures.
 Here is an
 example of
 how you might
 design a menu
 procedure to
 look.
 A menu is a
 screen
 procedure
 that lets you
 pick from a
 list of
 "menu items".
 When a menu
 item is
 picked, a
 corresponding
 procedure is
 called.
 Procedures
called:
> SHO_NAME
> SHO_COMPANY
> RPT_NAME
> RPT_COMPANY
> CARDS
> LABELS
> RETURN
 This is the Application Summary
 window.  You may remember seeing it
 in the introductory tutorial, but it
 probably didn't mean much to you at
 that time.  The schematic might now
 start to make a little more sense.
 Execution begins at the top of the
 schematic with MAIN_MENU.  This is
 what is known as the "base procedure".
 The lines branching off from MAIN_MENU
 show the procedures that are called
 when a menu item is selected in the
 menu procedure.
 Here is an example of how a table procedure might look.
 A table is a screen procedure that displays a scrollable
 list of records from a file.  The selector bar is moved up
 and down with the Up and Down arrow keys.  The Enter key
 is used to select a record.  A table procedure can specify
 an "update procedure" which gives it the ability to call a
 procedure to handle adding new records, or revising or
 deleting existing records.
 The schematic shows the table
 procedure SHO_NAME.  SHO_NAME
 calls UPD_PHONES, the update
 procedure for the table.
 You can see from the schematic
 that UPD_PHONES calls a
 procedure named SHOW_STATE,
 which in turn calls a procedure
 named UPD_STATE.
 This is UPD_PHONES, a form procedure and the update procedure called
 by SHO_NAME.  A form is a screen procedure where you can type data
 into the fields of a file's record.  This type of screen is sometimes
 also called a data entry screen.
 These characters are called "field prompts".
 Prompts help to show where a data entry field
 begins, and which field in the data file is
 being entered.
 These are the data entry fields of the
 form.  The first field is shown with
 reversed colors because it is the
 "selected field", or the field that is
 currently being entered.
 A form procedure can also call another procedure.  This entry field has a
 look-up procedure specified.  When you enter data into the state field, the
 look-up procedure is called.  Table procedures are often used as look-up
 procedures.
 This table procedure (used as a look-up procedure) also has an update
 procedure.  These screen procedures show how two files can be related in
 a program.  The PHONES and STATES files are related through the state code
 field.  While starting out to revise a phone book record, if necessary, you
 will have the ability to add a new state code.
 Once you have decided how many data files you will need,
 what keys they will have, and what fields will make up
 their records, the next step is to decide what needs to
 be done with this data.
 For example, you will have to have ways of entering the
 information so that records can be added to data files.
 You will also need to be able to revise or delete existing
 records.  You probably have in mind reports you would like
 to have printed.  In order to accomplish these tasks, the
 computer needs to be given instructions.  The instructions
 must be very explicit.  The computer must be told every
 step it must take and in what order to take each step.
 update procedure for SHO_NAME
 look-up procedure
 update procedure
 The schematic shows you how these
 procedures are "hooked together".
 This menu item calls a procedure named RPT_NAME which is a
 report procedure.  A report procedure prints a report on
 your printer.  A report can have a title page, a page
 heading and page footing, and repeated rows of data which
 can be grouped, totaled, or averaged.
 This is what the report looks like when
 it prints on your printer.
 Mo |  9/01/88
Personal Telephone Directory
Page 1
List by Name
 &o |
 O| Name
Company
Telephone
 O| Callaway, Rob
Acme Computer Products
-1212
1020 W. 31st St
Coral Way
o | Garrison, Tom
Wilson Distributing
-4455
167 Plantation Rd.
 "o |
Coral Way
| Harrison, Brian
     Harrison Pool Service
-6789
13 Scottish Blvd
Coral Way
 This concludes the tutorial on procedures.  As with the
 files tutorial, the goal was to present to you a number of
 of terms and concepts that will be used in later tutorials
 and in your user's manual.
 We still have said little about how to actually use
 Personal Developer, but the wait is now over.
 The next tutorial shows how to use Quick Start.  You will
 see how to begin to build programs using the file, key,
 and procedure concepts you have learned thus far.
 With a traditional programming language, it is the job of
 a programmer to write the instructions that make up the
 program.  This process is time consuming, somewhat of an
 art, and often hampered by human error.
 With Personal Developer, the necessary statements of the
 programming language are generated for you.  You will
 denote major tasks to be done (not the individual steps)
 and describe the way you want those tasks to work and how
 your screens and reports will appear.  Personal Developer
 will write the program, creating the language statements
 needed to do the job in the most efficient manor.
 The major tasks that you will be designing are
 called "procedures".
 A procedure consists of a set of instructions.
 When these instructions are performed by the
 computer we say that the computer is
 "executing" the instructions.  (Or we can say
 that the procedure is being "executed.")
 The last instruction to execute in a procedure
 is the "Return" instruction.  We say that a
 procedure "returns" when it is finished.
 Procedures must be named.  A
 procedure begins to execute
 when an instruction "calls"
 the procedure by its name.
 In this example, when "A"
 calls "B", procedure "A"
 stops executing and procedure
 "B" begins to execute.
 When "B" finishes it returns
 to the procedure that called
 it.  In this case, execution
 will begin again at the
 instruction following the
 point at which "B" was called.
 Called procedures may call
 other procedures.  There is
 almost no limit to how "deep"
 this sort of calling can go,
 but there are some rules.
 A procedure cannot call itself.
 If it did it, it would find itself in an
 "endless loop", calling itself forever
 -- chasing its tail, so to speak.
 Likewise, procedure "C" cannot call "A"
 or "B" because they will cause "C" to
 be called again.
 Another case of endless tail chasing.
 Personal Developer allows you to create four types of
 procedures in your programs:
     Menus, Tables, Forms, and Reports.
 Menus, tables, and forms are "screen procedures".
 That is, they use the screen of your computer's
 monitor to display information, and they use your
 computer's keyboard to accept information from you.
 A "report procedure" prints information on your
 computer's printer.
Name field
>Address field
>City, State, Zip field
>Phone number field
Birthday field
File
Record
 (Record
 (Record
 (Record
  Use Quick Start?:Yes  Yes No
 If you press Enter
 for the Create
 option, the Quick
 Start option
 window appears.
 Quick Start is a
 fast way to create a simple application.  You can
 learn more about Quick Start in its tutorial.
 >Design New Application
 4Create
 The last Base Window option is [Quit].  As
 you might expect, pressing Enter here will
 take you out of Personal Developer and
 return you to DOS.
 RExit to DOS
Quit
 The [Run] option "runs" an application.
 -Run Selected Application
Personal Telephone Directory
State Listing
FL  Florida
GA  Georgia
IA  Iowa
IL  Illinois
IN  Indiana
KY  Kentucky
MD  Maryland
ME  Maine
MO  Missouri
 to point
ENTER to select
 INS to add  DEL to delete  ESC to exit
Personal Telephone Directory
  Listing by Name
  Callaway, Rob
Acme Computer Products
     305/
-1212
  Garrison, Tom
Wilson Distributing
-4455
  Harrison, Brian
Harrison Pool Service
-6789
  Johnson, Bill
Dynamic Resorts, Inc.
305/837-4456
  Madison, Steve
Coral Way Bank
-7790
  Morrison, Alan
MTD Software Services, Inc.
-1176
  Nicholas, Randy
Info-Tronic Subsystems, Ltd.
314/335-6749
  Patterson, Corry
Floppy Disks Galore, Inc.
402/771-9648
  Shannon, Manny
Indispensible Software
     305/
-3895
  Stanton, Bob
Clarion Software
305/785-4
  Woodson, Mary
Acme Computer Products
     305/
-1212
 to point  ENTER to select  INS to add  DEL to delete
Press ESC once to use locator field and again to exit to the menu.
 And of course the tutorial option allows
 you to view these screens that you are
 seeing now.
 EPersonal Developer Tutorial
 \Tutorial
Update Directory
Record will be Changed
  Name
:Johnson, Bill
  Company :Dynamic Resorts, Inc.
  Address :56 Plum Ave
  City
:Largo
  State
  Zip
:33050
  Phone
:305/837-4456
State Listing
Record will be Added
  Code :
  State:
N(OONN
APPS
APPWIN  .
ATTRS
BAR
BASE
BEGIN   j
BLACK
CARD1
CARD2   =
CARD3   ]
CARD4
CARDS
COLORS
CONC_W1
CREATE
FIELDWIN
FILE
FILE2
FILEWIN
FILE_W1
FILE_W10y:
FILE_W11g<
FILE_W12
FILE_W13
FILE_W14
FILE_W15GC
FILE_W16
FILE_W17
FILE_W18
FILE_W19SH
FILE_W2 QI
FILE_W20
FILE_W3
FILE_W4
FILE_W5
FILE_W6 ]S
FILE_W7
FILE_W8
FILE_W9
IMP_EXP
INSTR1
INSTR2  k`
INSTR3
INTRO_W1
INTRO_W2Mi
INTRO_W3*j
INTRO_W4
INTRO_W5[l
KEY1    Zn
KEY2
KEY3
KEYWIN
MENU
MODIFY
MODIFY2
OPTIONS
OPTWIN
OPT_W1
OPT_W10 0
OPT_W11
OPT_W2
OPT_W3
OPT_W4
OPT_W5  +
OPT_W6  9
OPT_W7  g
OPT_W8
OPT_W9
PCLARION
PHONES
PROC1
PROC2   Q
PROC3
PROC4
PROC_W1
PROC_W10
PROC_W11
PROC_W12I
PROC_W13
PROC_W14#
PROC_W15
PROC_W16
PROC_W17
PROC_W18/
PROC_W19h
PROC_W2
PROC_W20
PROC_W21
PROC_W22
PROC_W23
PROC_W3
PROC_W4
PROC_W5
PROC_W6
PROC_W7
PROC_W8
PROC_W9
PT_FIELD
PT_FILE
PT_RECS
QUICK   o
QUIT
RUN     Z
SHOW_STA
SHO_NAME{
TUTOR   L
UPD_PHONq
UPD_STAT